How to resolve the "private/public divide" to suit your needs
nisbot.iconWhat would you like to see happen in this conversation?
nisbot.iconWhat kind of "private/public divide" is that "private/public divide"?
nishio.iconThe problem that what is written in private and what is written in public are not linked.
nisbot.iconWhat kind of "PRIVATE" is that "PRIVATE"?
nishio.iconI can't write about it in public for reasons I can't disclose.
nisbot.iconWhat kind of "public" is this "public"?
nishio.iconI have a need to share with others promptly, and I'm not happy if it's forwarded once a day after writing in PRIVATE, and it's probably a hassle to forward it manually after writing it.
nisbot.iconIs there anything else about that "PRIVATE"?
nishio.iconI created a program to discover links between projects, considering them to be independent from public, but I felt that this was not the case either. I still think it is better for the project to be an integral part of the public project, including the contents of the public project.
nisbot.iconIs there anything else about that "public"?
nishio.iconWhen making a naive transfer from public to private, if you make additions on the private side, they will be overwritten. Example: Putting a link to a private PDF on the book's introduction page
nisbot.iconWhere is that "PRIVATE"?
nishio.iconListen first.
nisbot.iconYes, sir.
nishio.iconThe reason why the title is overwritten by the transfer is because the title is the same; why not just put the key emoji in the title of the private page?
nisbot.icon「private」
nishio.iconIt would be nice if there was a UserScript that could easily create this key page in a private project.
nisbot.icon「private」
nishio.iconPlace a link to the original page using the page with the key icon.
nisbot.icon「private」
nishio.icon(of) good appearance
nisbot.icon「private」
nishio.iconthe end
nisbot.iconWhat would you like to see happen in this conversation?
nishio.iconIt would have been nice to know how to resolve the "private/public split" to suit my needs: overwrite transfer from public to private, don't update the public page in the private project, and provide an easy way to create key pages.
nisbot.iconHow do you know its "PRIVATE"?
nishio.iconI know because I make it myself.
nisbot.icon
It would have been nice to know how to resolve the "private/public split" to suit my needs: overwrite transfer from public to private, don't update the public page in the private project, and provide an easy way to create key pages.
Where is this "PRIVATE" located?
nishio.iconThe public page contains the contents of the public page, so searches and other operations will be performed on this page. You can write directly in public, or you can create a key page in private, write it, and then paste it into public. (There is no support here now, but it is good because it is infrequent in the current operation.)
nisbot.iconWhat is it that you value?
nishio.iconI want links to occur between the content that cannot be made public and the various pages I have written on the public project, so that awareness and reminders of the private content can occur.
nisbot.icon
The content of public will be included, so searches, etc. will be performed against this page. You can write directly in public, or you can create a key page in private, write it, and then paste it into public (there is no support here now, but it is good because it is infrequent in the current operation).
What do you hope will happen regarding this "private"?
---
This page is auto-translated from /nishio/自分のニーズに合った「private/public分断」解消の方法 using DeepL. If you looks something interesting but the auto-translated English is not good enough to understand it, feel free to let me know at @nishio_en. I'm very happy to spread my thought to non-Japanese readers.